CI Build iCube enables you to create ad hoc reports that help you to track the status of your software development builds, jobs, tests, and analyze the success or failure of builds. This iCube generates reports to view success or failure of a build lets you analyze the reason for build failure.
Attribute | Description |
---|---|
Build Date | The date on which the build was initiated |
Build Definition Description | A short description of the build |
Build Definition Name | Name of the job |
Build Definition Type | A list of values to select the type of job |
Build Definition URL | Link to the job |
Build End Date | Date on which the build was completed |
Build End Time | The time at which the build was completed |
Build ID | The ID generated by the CI Server to identify a specific build. Project Plan Name and Build Number together uniquely identify each build |
Build Number | The number generated by the CI Server to identify a specific build. Project Plan Name and Build Number together uniquely identify each build |
Build Result |
The Result of the Build execution is stored in this field, some of the metrics are dependent on this field. Here's the Source - Data warehouse mapping:
Supported only for Microsoft Azure DevOps Service source. |
Build Start On | The date on which the build started |
Build Start Time | The time at which the build started |
Build Status | For Jenkins: It is the status of the build upon completion. The result is a value from a defined list of values —SUCCESS, FAILURE, UNSTABLE, ABORTED. For Microsoft Azure DevOps Service, it is the status of the build at a given point of time. The result one of the following values: Aborted, Success, In progress, or New. |
Build Type | A list of values to select the type of build |
Buildable Flag (Y/N) |
Flag to indicate if the job is active or disabled. Supported only for Jenkins source. |
Calendar Month | Gregorian calendar month displayed in the format 'Mmm YYYY' |
Calendar Quarter | Gregorian calendar quarter displayed in the format 'Q# YYYY' |
Calendar Week | Gregorian calendar week displayed in the format 'Mmm W#' |
Calendar Year | Gregorian calendar year displayed in the format 'YYYY' |
Last Build |
Job name and job start date of the Last Build. Supported only for Jenkins source. |
Last Completed Build |
Job name and job start date of the last completed build. Supported only for Jenkins source. |
Last Failed Build |
Job name and Job Start Date of the last Failed Build. Supported only for Jenkins source. |
Last Stable Build |
Job name and Job Start Date of the last Stable Build. Supported only for Jenkins source. |
Last Successful Build |
Job name and Job Start Date of the last Successful Build. Supported only for Jenkins source. |
Last Unstable Build |
Job name and Job Start Date of the last Unstable Build. Supported only for Jenkins source. |
Last Unsuccessful Build |
Job name and Job Start Date of the last Unsuccessful Build. Supported only for Jenkins source. |
Metric | Description | Formula/Condition | Expected Value |
---|---|---|---|
Actual Build Duration (Secs) | Amount of time (in seconds) taken by a build to complete | Sum(Actual Duration (Secs)) | >0 |
Avg Attempted Build |
Average number of build attempted based on Build Count. Supported only for Microsoft Azure DevOps Service source. |
(([Build Count] - [Successful Builds])/[Build Count]) | >0 |
Avg Successful Builds |
Average number of successful builds. Supported only for Microsoft Azure DevOps Service source. |
([Successful Builds]/[Build Count]) | >0, Closer to Build Count value is ideal |
Build Count | Count of all builds. | Count([Build Count]) | >0 |
Build Stability Score % |
Percentage of successful builds which are part of a job. Supported only for Microsoft Azure DevOps Service source. |
[Successful Builds]/ [Build Count] | >0%, Closer to 100% is ideal |
Estimated Build Duration (Secs) |
Amount of time (seconds) estimated for a build to complete. Supported only Jenkins source. |
Min([estimated duration]) | >0 |
Tests Failed |
The number of test cases that failed for a job build. The value reported is a roll-up or aggregate of all child builds. Supported only for Jenkins source. |
Sum([automated test fail count]) {~} | >=0, Closer to 0 is ideal |
Tests Failed % | Percentage of test cases that failed for a job build. The calculation includes test cases from child jobs. Supported only for Jenkins. | [automated test fail count] / [automated test total count] | >=0%, Closer to 0% is ideal |
Tests Passed | The number of test cases that were successful for a job build. The value reported is a roll-up/aggregate of all child builds. Supported only for Jenkins. | Sum([automated test pass count]) {~} | >=0 |
Tests Passed % | Percentage of test cases that were successful for a job build. The calculation includes test cases from child jobs. Supported only for Jenkins. | [automated test pass count] / [automated test total count] | >0%, Closer to 100% is ideal |
Tests Skipped | The number of test cases skipped (not run) for a job build. The value reported is a roll-up/aggregate of all child builds. Supported only for Jenkins. | Sum([automated test skip count]) {~} | >=0 |
Tests Skipped % | Percentage of test cases skipped (not run) for a job build. The calculation includes test cases from child jobs. Supported only for Jenkins. | [automated test skip count] / [automated test total count] | >=0%, Closer to 0% is ideal |
Tests Total | The total number of test cases for a job build (sum of Tests Passed, Failed and Skipped). The value reported is a roll-up/aggregate of all child builds. Supported only for Jenkins. | Sum([automated test total count]) {~} | >=0 |
Related Topics
© 2022 Digital.ai Inc. All rights reserved.